(1.37.109.15/16.2) id AA047365548; Fri, 23 Jun 1995 23:32:28 -0700
Return-Path: <owner-lightwave@webcom.com>
Received: from nova (nova.unix.portal.com) by webcom.com with ESMTP
(1.37.109.15/16.2) id AA047295544; Fri, 23 Jun 1995 23:32:24 -0700
Received: from hobo.online.portal.com (hobo.online.portal.com [156.151.5.5]) by nova (8.6.11/8.6.5) with ESMTP id XAA02161 for <lightwave@webcom.com>; Fri, 23 Jun 1995 23:35:48 -0700
From: Jeric@cup.portal.com
Received: (pccop@localhost) by hobo.online.portal.com (8.6.10/8.6.5) id XAA04712 for lightwave@webcom.com; Fri, 23 Jun 1995 23:35:47 -0700
To: lightwave@webcom.com
Subject: Re: Re Morphing
Lines: 23
Date: Fri, 23 Jun 95 23:35:47 PDT
Message-Id: <9506232335.1.4697@cup.portal.com>
X-Origin: The Portal System (TM)
Sender: owner-lightwave@webcom.com
Precedence: bulk
>>>Earlier version of lightwave would mess up the point order when copying and
>pasting objects. What you want to do is save your object to disk and load
>it into other layers to preserve the point order. BTW 4.0 doesn't have this
>problem.<<
>
>I just have to correct you on your last point. 4.0 for WindowsFWG does have
>this problem! Point order is too easily screwed up with cut/copy/paste,
>undo, metaform, mirror, merge points, all else remaining equal.
Gee, no kidding.
You should expect point order to change in those instances. It's
situations that involve saving/loading identical objects where the